The Arsenal Files 8/The Arsenal Files Collection #8 (Arsenal Computer) (1996).ISO/doorware/jewel26.zip/JEWEL.DOC

Text File | 1996-11-29 | 25KB | 595 lines

                   * * *  J E W E L   T H I E F * * *
          Copyright 1994, 1995, 1996 by Mike Jordan, M & S Software

Jewel Thief Version 2.6
11/21/1996 by M & S Software

Author: Mike Jordan

Built in BBS Support For:

  Wildcat! BBS 3.X, 2.X, 1.13       PCBoard BBS 14.X           QuickBBS
  Remote Access                     Spitfire BBS               GAP BBS
  RBBS-PC BBS                       T.A.G. BBS                 Searchlight

  (and any others that use the same drop file as these)

*** Game Description ***

Jewel Thief is a multi-level action game, with the object being to
steal as many jewels as you can without getting caught and Zapped
by the guards.  Jewel Thief is now InterBBS playable. This means
that you can create a League with other boards and compete for the
highest score and level. InterBBS play brings a whole new level of
excitement to the game.

Jewel Thief does not require a Demo Key nor does it expire.  It has no
annoying beeps, whistles, slow downs or other devices to get you
to register.  The registered version does have a few features not
found in the non-registered version though. Non-registered only works
in single node mode*, scores are reset after 21 days and bulletins are
not created.  In addition the makeup and play-ahead feature is only
available in the registered version of Jewel Thief.

Also only available to registered Sysops of Jewel Thief, is the Special
offer of a free registration to any of my other games.  There are 3
special levels in Jewel Thief, 40, 60, 80, that will generate a message
file and special code that will validate a claim for a free registration.
Read the READ-JT file for more details.

*Single Node Note: What this means is that if you are a multi-node
BBS that two people can not play Jewel Thief at the same time, BUT, the game
can still be accessed from ALL Nodes.  If someone is playing on Node 1 and
another person tries to play on Node 2, they will get a message that the game
is in use and to try back later.

*** Warranty ***

This product is provided "as is" without warranty of any kind. The entire
risk as to the results and performance of the program is assumed by you.
Furthermore, the author does not warrant, guarantee, or make any representa-
tions regarding the use of, or the results of the use of the program, and you
rely on the program and results solely at your own risk. The author cannot
accept responsibility for system damage, loss of profit, or any other special,
incidental, or consequential damages resulting from the use of or inability to
use this product.

*** Licensing ***

Upon registering you are granted a licensed JEWEL.KEY, which gives you
certain limited rights to use Jewel Thief.

You are granted the use of Jewel Thief on a single BBS System.
It may be used on several CPUs in a Networking or Multi-Tasking environment
where the BBS System has more than one physically connected node (i.e.
LAN Network).

You do not become an owner of Jewel Thief.  M & S Software retains
all rights to the software, copies of the software and related
materials. Also upon registering, you agree to use reasonable efforts to
protect the registered JEWEL.KEY file from unauthorized use, reproduction
and distribution.  All rights not specifically granted in this license are
reserved by M & S Software.

Failure to comply with this License can result in termination of the
License without refund.

*** Shareware Version ***

*** Shareware Concept - No Set Demo Period - Please Read ***

This door game is distributed under the SHAREWARE concept.  This
concept gives you the chance to "try before you buy", and see if it
meets your needs.

I've decided to break away from the standard "30 day trial period"
that many door authors are using and instead go to a much simpler
and more realistic policy. This is simply; Try it on your BBS.
If you like it and your users like it, then register it.  If it's not
good enough to register, then delete it.

While I'd like you to register my doors as soon as possible, I'm also
realistic enough to know that different boards have different requirements
and interests, and sometimes it takes longer befor a game catches on, or a
sysop can get to the Doors on his list to register.  And frankly, I'd rather
you ran it for awhile and register, than try it for a short period of time
and delete it. Nobody wins that way...I lose out on a registration and your
users lose out on the chance of having the registered door to play.


*** Four Ways To Run Jewel Thief ***

1.  Running Locally:

To run locally you must first create a JEWEL.CFG file.  To create this file
run JEWEL SETUP and fill in the fields that are presented. The .CFG file can
also be created or edited with any ASCII editor.  See the example JEWEL.CFG
file for the lines required.

Once the JEWEL.CFG file is created go to the DOS prompt and type:

        JEWEL JEWEL.CFG LOCAL

By specifying the configuration file, the game will use the Sysop's real
name instead of the name "Sysop".  It will also use the other parameters
in the JEWEL.CFG file that are active with the non-registered version.
If the registered JEWEL.KEY is present then all parameters will be
active.

2.  Running in Evaluation Mode:

Jewel Thief does not need a Demo Key to run in evaluation mode.  Create a
JEWEL.CFG and setup as described later in this documentation and you are
all set.  The evaluation mode will give you all the features of the
registered version EXCEPT that Bulletins will not be created, the multi-node
option will not function (it will still work on a multi-node BBS but two
callers can not play Jewel Thief at the same time) and the dedication line will
not be implemented. In addition the game will reset the score board every 21
days (the reset at the 1st of each month is normal) and continue as if it was
the first of the month.

3.  Running as a Registered Door:

You must have the Registration Key to run as a registered door. To register
simply print-out or copy the contents of the REGISTER.FRM file provided in
this package. Fill it out with the requested information and send it, along
with payment to the address on the form.  You may also call or send the
information by NetMail or upload it to my board for COD and Credit Card Orders.

Upon receipt of your order, you will be sent your registered key.  This
will be done, via Net-Mail where applicable, upload to your BBS if
possible or by U.S. Mail.  All COD orders will be sent UPS or U.S. Mail.
** Note: All COD fees will be added to the registration price.

4.  Running in InterBBS Mode:

Read the INTERBBS.TXT file for information on running Jewel Thief in
InterBBS mode.


*** Support ***

I will do my best to help with any problems encountered whether the game
is registered or not.

If you register this door, I will do my best to ensure that the registered
key is sent promptly.  I will do the best I can to support this door and
resolve any problems that might arise.  I can't guarantee to fix or resolve
all problems since there are so many different combinations of hardware,
software and system configurations being used, but I will do my best.

Support can be obtained by calling voice, my BBS, by mail or though the
FIDO Network. My current Node addresses are 1:105/314, 1:105/317, 1:105/330.
I also participate in the FIDO echos DOORWARE, On-Line-Games and DOORGAMES
as well as the MSI-WILDCAT echo and will answer any questions addressed to me.
See the SUPPORT.TXT file for more phone numbers and locations.

*** Features ***

       * Supports Wildcat 1.13-4.0+ & IM, QuickBBS, PCBoard 14.X, Gap,
         Spitfire, RBBS-PC, Remote Access 1.x & 2.x, T.A.G., WWIV, Telegard,
         Synchronet, TriBBS, VBBS, Ultra BBS, PowerBBS, Powerboard,
         Renegade, Searchlight (and any others that use these same type Door
         drop files) without the use of converters.

       * Detects & Adjusts Screen For RIP Graphics. Eliminates the
         scrunched screen appearance.

       * Makeup and Play ahead feature. (Requires Registered Key)

       * File Sharing & Record Locking for Networks & Multi-Tasking Systems.
         (Feature requires Registered Key File.)

       * DESQview Detection & Awareness, which speeds program execution.

       * Complete Setup Program to create the JEWEL.CFG file.

       * Full ANSI Game.

       * Full Spilt-Screen Chat.

       * Sysop can Add or Decrease Time allowed in door with function keys.

       * Sysop can force user back to BBS with function key.

       * Mono selected colors for sharp picture when played in Mono Mode.

       * Built in bulletin generator for ANSI and ASCII bulletins (registered
         version only).

       * Selectable In-depth Log File capability.

       * Carrier Drop Detection.

       * No Input In 5 Minutes, Time Out Detection.

       * Full BBS and FIDO Support (Demo or Registered)

       * Supports Comm Ports 1, 2, 3 & 4 And Non-Standard IRQ selection.

       * Supports Locked DTE Rate up to 115,200 Baud.

       * Supports FOSSIL and DigiFossil detection


*** Files In Archive ***

The following files are found either in the JEWEL.ZIP or will be
created during the runtime execution.

JEWEL.EXE    <--- Executable Program.

EXAMPLE.CFG   * <--- Sample Configuration File.

JEWEL.DAT  * <--- Store User's Name, Last Play Date & Scores.

JEWEL.HPS    <--- Ansi Mode Instructions Used By Program.

JEWEL.DOC    <--- This File.

JEWEL.SLB    <--- Screen Library.

JEWEL.CHP  * <--- Last Month's Champion File.

JEWEL.LOG  * <--- Game Activity Log.

DOOR.BAT        <--- Simple Sample Batch File For Door Execution.

REGISTER.FRM    <--- Registration Form For This And Other Doors.

HISTORY.TXT     <--- History file listing changes.

UPGRADE.TXT     <--- Explains what is needed to upgrade to new release
                     from previous one.

JEWEL.KEY       <--- Registration key. (Not needed for Evaluation mode)

SUPPORT.TXT     <--- List of boards carrying the latest version.

FOSSIL.TXT      <--- Information on Fossil support

JEWEL.INF     * <--- File used between Nodes to show who else is playing

JEWEL.FBK       <--- File  created when player leaves FeedBack message

JEWEL.MSG       <--- Special Message File created when player hits level
                     40, 60 & 80.  Gives code to send back to author
                     for a free registration of any other door.

LEAGUE.JT       <--- Text file that is created with list of Nodes playing
                     in InterBBS game.  Created by Sysop.

MASTER.JT*      <--- This is the Master Score file created when the IBBS
                     program is run.  This is used in InterBBS play.

TIMESTMP.DAT*   <--- This is created and updated when the IBBS program is
                     run and is the Time Stamp used in the Master Score
                     screen.

WHOSWHO.DAT*    <--- This file holds the BBS and Sysop info when playing
                     in InterBBS mode.

JT-?.DAT*       <--- This is the individual Node score file that is passed
                     to the Hub Node. The ? is replaced with the number
                     that has been assigned in the LEAGUE.JT file.

IBBS.CHP        <--- InterBBS last month high scorer record for all the
                     InterBBS players.

NOFEEDBK        <--- Create this file if you want the Sysop Feedback option
                     turned off. It must be in the Jewel Thief directory.

JEWEL.xx        <--- Previous month's score file, where xx = month number.

MASTER.xx       <--- Previous InterBBS Master score file.

* DENOTES that file is created during RUN-TIME.

JEWEL.CHP:

This is the Last Month's Champion file. It contains the Champ's Name, Score,
Date and How many games won that month. This file is automatically created
when the game is first executed.

Deleting the JEWEL.CHP file will cause the game to re-initialize
itself. It will create a new JEWEL.CHP, JEWEL.INF and a new JEWEL.DAT
file.

*** Setup & Installation ***

Installation procedures are very simple if you have setup a live program in
the past. First create a Sub-Directory for the door game and copy all the
files from the JEWEL.ZIP file into this directory.

Now execute the Setup program by typing JEWEL SETUP with no parameters at
the DOS prompt.  You must be in the directory with JEWEL.EXE.

This will run the game's setup feature that will create a JEWEL.CFG
file. The setup program has complete on-line help so I will not duplicate
them here.

Single Node Setup:

** See the section on Multi-Node for the changes
   required to line 1 and 6 in a Multi-Node setup.

This is what the JEWEL.CFG contains when created (less the comments).

   1                        <-- COM PORT 1, 2, 3, 4 or &H###/#
   N                        <-- Multi-Node 'Y' or 'N'
   COM-DAT BBS              <-- Name Of BBS
   Mike Jordan              <-- Sysop's Full Name
   DOOR.SYS                 <-- BBS Callers File
   C:\WC30\WCWORK\NODE1\    <-- Drive & Path Of System's Caller File
   LOG                      <-- LOG to keep user log or NOLOG to disable
   C:\BULLETIN\BULL99.BBS   <-- Drive\Path\BulletinName For Ascii Scores
   C:\BULLETIN\BULL99.ANS   <-- Drive\Path\BulletinName For Ansi Scores
   Wildcat                  <-- Type of BBS System You're Running See Note 1
   Thanks For The Donations <-- 50 character dedication line
   3                        <-- Games Allowed Per Day (1 to 99)
   3                        <-- Number of Days allowed for Makeup
   10                       <-- Day that Makeup Games Start
   1                        <-- Number of Nodes you have (1 for single node)
   1.5                      <-- Guard Movement Action Index (higher # = Slower)
                                Valid Range is anything between 1 and 2

NOTE 1: Valid System Callers files for each BBS system are as follows:

            Wildcat 3.- 4.X BBS System     <->  USERINFO.DAT or DOORS.SYS
            Wildcat! 1.X & 2.X BBS System  <->  CALLINFO.BBS
            QuickBBS System                <->  DORINFOx.DEF
            RBBS-PC BBS System             <->  DORINFOx.DEF
            Remote Access 1.x BBS System   <->  DORINFOx.DEF
            Remote Access 2.x BBS System   <->  DORINFOx.DEF or DOORS.SYS
            T.A.G. BBS System              <->  DORINFOx.DEF
            PCBoard BBS System             <->  PCBOARD.SYS
            Gap BBS System                 <->  DOORS.SYS
            Spitfire BBS System            <->  SFDOORS.DAT

If you use another BBS System besides those listed, then you must use
a converter to convert to one of the above caller file formats.

** The Bulletin Drive\Path\Bulletin Name is designed to accept any valid
Drive, Path and Filename of your choice. This allows each BBS system to
configure for it's individual system.

Note 2: Line 11 (the dedication line) is required, even
if it is a blank line.

*** Execution ***

Some BBS Systems call batch files and some run doors directly. If you
don't know how to install a door on your particular BBS System then please
see your BBS manual. This game merely needs the .CFG file name passed to it
on the command line to operate, i.e.

          JEWEL.EXE JEWEL.CFG

An example JEWEL.BAT file could look like this:

     C:                      <-- Change to drive door is in
     CD \JEWEL               <-- Change to door directory
     JEWEL.EXE JEWEL.CFG     <-- Execute door with config file
     CD\BBS                  <-- Change back to BBS (may not be needed)


Some systems (particular those with 486 PCs) may need to put in the
FOSSILOFF command.  This would look like this:

   JEWEL.EXE JEWEL.CFG FOSSILOFF

  Read the file FOSSIL.TXT included in the JEWEL.ZIP file.

*** Multi-Node Use ***

Running this game on more than a single node requires a Multi-Node Key.
When running in Evaluation mode, only one (1) Node will be able to access the
door at a time, but all nodes will be able to access the game.

*** Environmental Variable Support ***

    Setting Ports using Environment Variables: If your running a Multi-Node
  BBS system then you need to use environment variables. The game allows any
  variable name to be used, but I will use the name WCPORTID just for
  clarity. To specify the port using an environment variable you place the
  name of the variable on this line wrapped in percent signs, ie %WCPORTID%.
  This will tell the game to read this variable from the environment to get
  the com port information. One limit to this is the syntax which must keep in
  context when not using variables and this is when using non-standard port
  addressing. When using non-standard port addressing the syntax must be the
  same as explained above (ie. &H3F8/5). Some BBS packages use a different
  variable for each of these. If this is your case then merely create another
  by adding SET WCPORTID=&H3F8/5 to your BBS starting batch file and then use
  %WCPORTID% as the com port of the configuration file. See Multi-Node Setup
  below for more information.


    The setup of Jewel Thief changes the way my previous doors are setup.
  I now support and require the use of Environment Variables to supply the
  game with the Com Port and Node Directory information. The game will
  read any environment variable that you supply so names are not critical.

    The game now only reads the JEWEL.CFG file and will not accept any
  other name for the configuration file. So this is the file that will contain
  the environment variables.

    The game requires only two pieces of information. This is the Com Port
  and Node Directory information and these must be supplied with environment
  variables.

    The environment variables is best set by your BBS's calling batch file.
  This is the batch file that starts your BBS. If your running a Wildcat or
  PCBoard BBS system then you probably already use the WCNODEID or PCBNODE
  environment variables. These variables should work fine. If your using
  another BBS system then you will probably have a similar variable. If not
  just use the default ones used below in the example setup.

    Since I run Wildcat! software I am going to use WCPORTID and WCNODEID for
  my example of setting up on a Multi-Node system.  Also I will assume you need
  to add the environment variables where in fact most cases they will already
  be in use.

Step 1:

    You will need to add the following lines to your batch files that start
  your BBS. These lines should be located near the top of the file ahead
  of any loop since they only need to be initialized one time:

     SET WCPORTID=1    This is your com port environment variable
                       and assigns the com port for each node.

     SET WCNODEID=1    This is your node id environment variable
                       and assigns the node number for each node.

    The WCPORTID is the tricky one of the two. Where the WCNODEID merely
  assign the node number the WCPORTID may also have to assign a Non-Standard
  Port address and IRQ. See above 'Line #1 Com Port' for explanation of this.


    I will give a few examples setting the WCPORTID variable to try to avoid
  confusion.

     SET WCPORTID=2         '--- Use Com Port #2 with IRQ 3 (standard)

     SET WCPORTID=&H3E8/5   '--- Use Com Port #3 with IRQ 5

**Note: Both the SET command and the matching *.CFG line must be in ALL CAPs.

    The environment variables are used on lines #1 and #6 of the configuration
  file. Below is the first 7 lines of the configuration file with the
  environment variables in place. See above if you need to see the complete
  file. (exclude the comments).

    %WCPORTID%                <-- COM PORT 1, 2, 3, 4 or &H###/# or %WCPORTID%
    Y                         <-- Make Sure This Is 'Y'es
    Com-Dat BBS               <-- Name Of BBS
    Mike Jordan               <-- Sysop's Full Name
    DOOR.SYS                  <-- BBS Drop File
    C:\BBS\NODE%WCNODEID%\    <-- Drive & Path Of Systems Caller File
    LOG                       <-- LOG to keep user log or NOLOG to disable
    ...etc...

    The game will read in these lines and will check lines #1 and #6 for
  environment variables and thus read in their information. Line #6 assumes
  the DOOR.SYS file will be placed in the C:\BBS\NODE1\ sub-directory if
  WCNODEID equals 1.

    If you are already using environment variables with your current BBS setup
  that meet the games need you can merely use those instead.

  That's all there is too it.


** COMMANDS **

    COMMAND Line Parameters: SETUP  LOCAL  ALIAS  FOSSIL  SPLIT  IBBS

    This door has several command line parameters listed above. Below is
    description for usage:

    SETUP       - Run's the Jewel Thief Setup program.

    LOCAL       - Used in conjunction with FILENAME.CFG LOCAL for executing
                  the door in local only mode. For use from the DOS prompt
                  only. Never use LOCAL in a BBS batch file.

    ALIAS       - Cause's the door to use Alias names on BBS System's
                  which support the DOOR.SYS drop file.

    FOSSIL      - Cause's the door to use a previously installed fossil.


    SPLIT       - Just a toy. This will cause the game to split the opening
                  registration screen from the display.

    IBBS        - This runs the InterBBS maintenance program.  It is used
                  to create the MASTER.JT, JT-?.DAT file and WHOSWHO.DAT
                  file.

    In some cases more than one option will be needed, such a case being
  when using a fossil and also using alias names. The command line to execute
  the game would look like this:

                           JEWEL.EXE FOSSIL ALIAS

                      Order of the option does not matter.


*** Notes Of Interest ***

This game does not require a monitoring program for dropped carrier as
it automatically detects this and exits back to the BBS.

This door DOES NOT require any runtime modules. It will run
as is without aid from outside utilities.


*** Technical Support ***

Voice Support & Order Number: [phone]

If you have problems with this door game you can contact me through
my BBS at the numbers listed below, or though my FIDO addresses 1:105/314,
1:105/317 or 1:105/330.

BBS Phone: Com-Dat
           Node 1 - [phone] (14.4 HST DS (Only 9600 at v32))
           Node 2 - [phone] (14.4 v32)
           Node 3 - [phone] (Hayes 28.8)
           FIDO 1:105/314 (14.4 V.32)
           FIDO 1:105/317 (14.4 V.32)
           24 hour - First time callers have access to door programs.

       or: Com-Dat II  (CM Mail and Door Support)
           Net Mail and File Requests of latest version
           FIDO 1:105/330 - Hayes 28.8
           E-Mail: [e-mail]
Mailing Address: Mike Jordan
                 2001 NE Hyde St.
                 Hillsboro, OR.  97124
                 Orders & Support Voice: [phone]

*** Ordering Information ***

Please see the file REGISTER.FRM file in this package for ordering
information.

*** Updates To M & S Doors ***

Updates to any M & S Software product may be downloaded from any Distribution
BBS.  My intent is to always supply updates FREE unless major revisions are
made to the software, in which case a small update fee will be charged. I do
charge for lost keys or if your BBS name changes.

*** Distribution ***

You are free, in fact encouraged, to distribute the SHAREWARE version
of the door game provided that all files contained in the original
archive are distributed in their original unmodified state.

The Registered Key MAY NOT be distributed in any form.

*** Acknowledgements ***

              Wildcat BBS System - Mustang Software
              GAP Communications - The GAP Development Company
              PCBoard - Clark Development Company, Inc.
              Spitfire - Mike Woltz, Buffalo Creek Software
              QuickBBS - The QuickBBS Group, Inc
              Remote Access - Wantree Development
              JNS Software - Rusty Johnson

*** Special Acknowledgement ***

I would like to give a very big thank you to the person that has done the
most to make this game (plus all my past and hopefully future door games)
possible.  This person is Rusty Johnson of JNS Software. Rusty has released
many excellent door games into the BBS arena and if you haven't taken a look
at any of them you are missing out on some of THE best door games available.
Rusty and I have known each other for several years now and have helped each
other many times and this is one case where giving has been rewarded tenfold.
I'm glad to be able to call Rusty my friend.  Thanks Rusty.


Jewel Thief Copyright 1994, 1995 by M & S Software